Do not migrate blur in wire:model.blur
#18216
Merged
+5
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Jordan Pittman <[email protected]>
thecrypticace
approved these changes
Jun 3, 2025
RobinMalfait
force-pushed
the
fix/issue-18187
branch
from
e49e90d to
0bea73a
Compare
RobinMalfait
force-pushed
the
fix/issue-18187
branch
from
0bea73a to
0ab96b7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where the
blurinwire:model.blur="…"was incorrectly migrated. We solved it by markingwire:…as an unsafe region (…can be anything but whitespace).Fixes: #18187
Test plan
Added a test with this use case